Techniques and apparatuses for carrier management

ABSTRACT

A method, base station (BS), user equipment (UE), apparatus, and computer program product for wireless communication are provided. A BS and a UE may communicate using a narrowband Internet of Things (NB-IoT) communication system. However, a frequency, time, and/or power associated with transmission of a SIB1-NB on a non-anchor carrier may not be configured for NB-IoT. In some aspects, the BS may determine parameters, such as a time domain location parameter, a frequency domain location parameter, a quantity of repetitions, a power boosting parameter, and/or the like for a transmission in NB-IoT. In some aspects, a UE may determine to transmit a connection request message on a different carrier than a random access channel message.

CROSS-REFERENCE TO RELATED APPLICATIONS UNDER 35 U.S.C. § 119

This application claims priority to Patent Cooperation Treaty (PCT)Patent Application No. PCT/CN2017/111308, filed on Nov. 16, 2017,entitled “TECHNIQUES AND APPARATUSES FOR CARRIER MANAGEMENT,” which ishereby expressly incorporated by reference herein.

BACKGROUND Field

Aspects of the present disclosure generally relate to wirelesscommunication, and more particularly to techniques and apparatuses forcarrier management.

Background

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, and/or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency-division multipleaccess (FDMA) systems, orthogonal frequency-division multiple access(OFDMA) systems, single-carrier frequency-division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless communication network may include a number of base stations(BSs) that can support communication for a number of user equipment(UEs). A UE may communicate with a BS via the downlink and uplink. Thedownlink (or forward link) refers to the communication link from the BSto the UE, and the uplink (or reverse link) refers to the communicationlink from the UE to the BS. As will be described in more detail herein,a BS may be referred to as a Node B, a gNB, an access point (AP), aradio head, a transmit receive point (TRP), a 5G BS, a 5G Node B, and/orthe like.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless communication devices to communicate on a municipal,national, regional, and even global level. 5G, which may also bereferred to as New radio (NR), is a set of enhancements to the LTEmobile standard promulgated by the Third Generation Partnership Project(3GPP). 5G is designed to better support mobile broadband Internetaccess by improving spectral efficiency, lowering costs, improvingservices, making use of new spectrum, and better integrating with otheropen standards using OFDM with a cyclic prefix (CP) (CP-OFDM) on thedownlink (DL), using CP-OFDM and/or SC-FDM (e.g., also known as discreteFourier transform spread ODFM (DFT-s-OFDM)) on the uplink (UL), as wellas supporting beamforming, multiple-input multiple-output (MIMO) antennatechnology, and carrier aggregation. However, as the demand for mobilebroadband access continues to increase, there exists a need for furtherimprovements in LTE and 5G technologies. Preferably, these improvementsshould be applicable to other multiple access technologies and thetelecommunication standards that employ these technologies.

A BS and a UE may communicate using a carrier. For example, innarrowband Internet of Things (NB-IoT) time division duplex (TDD)operation, a BS and a UE may communicate using a group of channels, suchas a broadcast channel, a shared channel, a downlink channel, an uplinkchannel, and/or the like, conveyed using at least one carrier. A firstphysical resource block (PRB) may include a narrowband primarysynchronization signal, a narrowband secondary synchronization signal,and/or the like. The first PRB may be the anchor carrier for a network.One or more second PRBs may be configured using system information blocksignaling, radio resource control signaling, and/or the like asnon-anchor carriers for paging, random access procedures, and unicasttransmissions.

A system information block type 1 narrowband (SIB1-NB) message may betransmitted on an anchor carrier, and may be multiplexed with anarrowband secondary synchronization signal, such as in a time divisionmultiplexed communication system. In some cases, the SIB1-NB may betransmitted on a non-anchor carrier, such as based at least in part onan indication associated with a master information block, which mayreduce inter-cell interference for the SIB1-NB, such as when a quantityof repetitions of the SIB1-NB from a set of neighboring cells is greaterthan a threshold quantity. However, a frequency, a time, a quantity ofrepetitions, a power, and/or the like associated with transmission of aSIB1-NB on a non-anchor carrier may not be configured.

SUMMARY

Some aspects, described herein, may provide a mechanism for carriermanagement. For example, a BS may determine a frequency domain locationparameter, a time domain location parameter, and/or the like fortransmitting a message. Similarly, a UE may identify a plurality ofcarriers, and may transmit a connection request message (e.g., a Msg3type message) using at least one of the plurality of carriers. In thiscase, the at least one carrier may be different for a connection requestmessage than for a random access channel message, thereby reducing atime delay associated with transmitting the connection request messageand reducing a likelihood of collision between the connection requestmessage and the random access channel message. In this way, the BS andthe UE may enable messaging using a non-anchor carrier, such as for aSIB1-NB message, a connection request message (e.g., a msg3 typemessage), and/or the like.

In an aspect of the disclosure, methods, a user equipment, a basestation, apparatuses, and computer program products are provided.

In some aspects, the method may include transmitting, by a base station,a master information block message including an indicator identifying afrequency domain location parameter or a time domain location parameterfor a non-anchor carrier or an anchor carrier. The method may includetransmitting, by the base station and using the non-anchor carrier orthe anchor carrier, a system information block type 1 (SIB1) message toa user equipment in accordance with the frequency domain locationparameter or the time domain location parameter.

In some aspects, the base station may include a memory and at least oneprocessor coupled to the memory. The memory and the at least oneprocessor may be configured to transmit a master information blockmessage including an indicator identifying a frequency domain locationparameter or a time domain location parameter for a non-anchor carrieror an anchor carrier. The memory and the at least one processor may beconfigured to transmit, using the non-anchor carrier or the anchorcarrier, a system information block type 1 (SIB1) message to a userequipment in accordance with the frequency domain location parameter orthe time domain location parameter.

In some aspects, the apparatus may include means for transmitting amaster information block message including an indicator identifying afrequency domain location parameter or a time domain location parameterfor a non-anchor carrier or an anchor carrier. The apparatus may includemeans for transmitting, using the non-anchor carrier or the anchorcarrier, a system information block type 1 (SIB1) message to a userequipment in accordance with the frequency domain location parameter orthe time domain location parameter.

In some aspects, the computer program product may include anon-transitory computer-readable medium storing computer executablecode. The code may include code for transmitting a master informationblock message including an indicator identifying a frequency domainlocation parameter or a time domain location parameter for a non-anchorcarrier or an anchor carrier. The code may include code fortransmitting, using the non-anchor carrier or the anchor carrier, asystem information block type 1 (SIB1) message to a user equipment inaccordance with the frequency domain location parameter or the timedomain location parameter.

In some aspects, the method may include transmitting, by the userequipment, a random access channel using a first carrier, of a pluralityof carriers, in a time division duplex network for random access. Themethod may include transmitting, by the user equipment, a connectionrequest message using a second carrier, of the plurality of carriers,that is different from the first carrier.

In some aspects, the user equipment may include a memory and at leastone processor coupled to the memory. The memory and the at least oneprocessor may be configured to transmit a random access channel using afirst carrier, of a plurality of carriers, in a time division duplexnetwork for random access. The memory and the at least one processor maybe configured to transmit a connection request message using a secondcarrier, of the plurality of carriers, that is different from the firstcarrier.

In some aspects, the apparatus may include means for transmitting arandom access channel using a first carrier, of a plurality of carriers,in a time division duplex network for random access. The apparatus mayinclude means for transmitting a connection request message using asecond carrier, of the plurality of carriers, that is different from thefirst carrier.

In some aspects, the computer program product may include anon-transitory computer-readable medium storing computer executablecode. The code may include code for transmitting a random access channelusing a first carrier, of a plurality of carriers, in a time divisionduplex network for random access. The code may include code fortransmitting a connection request message using a second carrier, of theplurality of carriers, that is different from the first carrier.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, access point, and processingsystem as substantially described herein with reference to and asillustrated by the accompanying specification and drawings.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purpose ofillustration and description, and not as a definition of the limits ofthe claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is diagram illustrating an example of a wireless communicationnetwork.

FIG. 2 is a diagram illustrating an example of a base station incommunication with a user equipment (UE) in a wireless communicationnetwork.

FIG. 3 is a diagram illustrating an example logical architecture of adistributed radio access network (RAN).

FIG. 4 is a diagram illustrating an example physical architecture of adistributed RAN.

FIG. 5 is a diagram illustrating an example relating to carriermanagement.

FIG. 6 is a diagram illustrating an example relating to carriermanagement.

FIG. 7 is a diagram illustrating an example relating to carriermanagement.

FIG. 8 is a diagram illustrating an example relating to carriermanagement.

FIG. 9 is a diagram illustrating an example relating to carriermanagement.

FIG. 10 is a flow chart of a method of wireless communication.

FIG. 11 is a conceptual data flow diagram illustrating the data flowbetween different modules/means/components in an example apparatus.

FIG. 12 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

FIG. 13 is a flow chart of a method of wireless communication.

FIG. 14 is a conceptual data flow diagram illustrating the data flowbetween different modules/means/components in an example apparatus.

FIG. 15 is a diagram illustrating an example of a hardwareimplementation for an apparatus employing a processing system.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appendeddrawings is intended as a description of various configurations and isnot intended to represent the configurations in which the conceptsdescribed herein may be practiced. The detailed description includesspecific details for the purposes of providing a thorough understandingof various concepts. However, it will be apparent to those skilled inthe art that these concepts may be practiced without these specificdetails. In some instances, well-known structures and components areshown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented withreference to various apparatus and methods. These apparatus and methodswill be described in the following detailed description and illustratedin the accompanying drawings by various blocks, modules, components,circuits, steps, processes, algorithms, and/or the like (collectivelyreferred to as “elements”). These elements may be implemented usingelectronic hardware, computer software, or any combination thereof.Whether such elements are implemented as hardware or software dependsupon the particular application and design constraints imposed on theoverall system.

By way of example, an element, or any portion of an element, or anycombination of elements may be implemented with a “processing system”that includes one or more processors. Examples of processors includemicroprocessors, microcontrollers, digital signal processors (DSPs),field programmable gate arrays (FPGAs), programmable logic devices(PLDs), state machines, gated logic, discrete hardware circuits, andother suitable hardware configured to perform the various functionalitydescribed throughout this disclosure. One or more processors in theprocessing system may execute software. Software shall be construedbroadly to mean instructions, instruction sets, code, code segments,program code, programs, subprograms, software modules, applications,software applications, software packages, routines, subroutines,objects, executables, threads of execution, procedures, functions,and/or the like, whether referred to as software, firmware, middleware,microcode, hardware description language, or otherwise.

Accordingly, in one or more example embodiments, the functions describedmay be implemented in hardware, software, firmware, or any combinationthereof. If implemented in software, the functions may be stored on orencoded as one or more instructions or code on a computer-readablemedium. Computer-readable media includes computer storage media. Storagemedia may be any available media that can be accessed by a computer. Byway of example, and not limitation, such computer-readable media cancomprise a random-access memory (RAM), a read-only memory (ROM), anelectrically erasable programmable ROM (EEPROM), compact disk ROM(CD-ROM) or other optical disk storage, magnetic disk storage or othermagnetic storage devices, combinations of the aforementioned types ofcomputer-readable media, or any other medium that can be used to storecomputer executable code in the form of instructions or data structuresthat can be accessed by a computer.

It is noted that while aspects may be described herein using terminologycommonly associated with 3G and/or 4G wireless technologies, aspects ofthe present disclosure can be applied in other generation-basedcommunication systems, such as 5G and later, including 5G technologies.

FIG. 1 is a diagram illustrating a network 100 in which aspects of thepresent disclosure may be practiced. The network 100 may be an LTEnetwork or some other wireless network, such as a 5G network. Wirelessnetwork 100 may include a number of BSs 110 (shown as BS 110 a, BS 110b, BS 110 c, and BS 110 d) and other network entities. A BS is an entitythat communicates with user equipment (UEs) and may also be referred toas a base station, a 5G BS, a Node B, a gNB, a 5G NB, an access point, atransmit receive point (TRP), and/or the like. Each BS may providecommunication coverage for a particular geographic area. In 3GPP, theterm “cell” can refer to a coverage area of a BS and/or a BS subsystemserving this coverage area, depending on the context in which the termis used.

ABS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or another type of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a closed subscriber group (CSG)). A BS for a macro cell may bereferred to as a macro BS. A BS for a pico cell may be referred to as apico BS. A BS for a femto cell may be referred to as a femto BS or ahome BS. In the example shown in FIG. 1, a BS 110 a may be a macro BSfor a macro cell 102 a, a BS 110 b may be a pico BS for a pico cell 102b, and a BS 110 c may be a femto BS for a femto cell 102 c. A BS maysupport one or multiple (e.g., three) cells. The terms “eNB”, “basestation”, “5G BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” maybe used interchangeably herein.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of amobile BS. In some examples, the BSs may be interconnected to oneanother and/or to one or more other BSs or network nodes (not shown) inthe access network 100 through various types of backhaul interfaces suchas a direct physical connection, a virtual network, and/or the likeusing any suitable transport network.

Wireless network 100 may also include relay stations. A relay station isan entity that can receive a transmission of data from an upstreamstation (e.g., a BS or a UE) and send a transmission of the data to adownstream station (e.g., a UE or a BS). A relay station may also be aUE that can relay transmissions for other UEs. In the example shown inFIG. 1, a relay station 110 d may communicate with macro BS 110 a and aUE 120 d in order to facilitate communication between BS 110 a and UE120 d. A relay station may also be referred to as a relay BS, a relaybase station, a relay, and/or the like.

Wireless network 100 may be a heterogeneous network that includes BSs ofdifferent types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, and/orthe like. These different types of BSs may have different transmit powerlevels, different coverage areas, and different impact on interferencein wireless network 100. For example, macro BSs may have a high transmitpower level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relayBSs may have lower transmit power levels (e.g., 0.1 to 2 Watts).

A network controller 130 may couple to a set of BSs and may providecoordination and control for these BSs. Network controller 130 maycommunicate with the BSs via a backhaul. The BSs may also communicatewith one another, e.g., directly or indirectly via a wireless orwireline backhaul. In some aspects, network controller 130 may determinea plurality of carriers that are to be used for communications. Forexample, network controller 130 may determine a first carrier for ananchor channel for narrowband Internet of Things (NB-IoT) time divisionduplex (TDD) communication, and at least one second carrier for anon-anchor channel for NB-IoT TDD communication. Additionally, networkcontroller 130 may transmit a message to cause a connection requestmessage to be transmitted using a different carrier than a random accesschannel request message, such as using a non-anchor carrier identifiedin a plurality of carriers.

UEs 120 (e.g., 120 a, 120 b, 120 c) may be dispersed throughout wirelessnetwork 100, and each UE may be stationary or mobile. A UE may also bereferred to as an access terminal, a terminal, a mobile station, asubscriber unit, a station, etc. A UE may be a cellular phone (e.g., asmart phone, such as UEs 120 b and/or 120 d), a personal digitalassistant (PDA), a wireless modem, a wireless communication device, ahandheld device, a laptop computer, a cordless phone, a wireless localloop (WLL) station, a tablet, a camera, a gaming device, a netbook, asmartbook, an ultrabook, medical device or equipment, biometricsensors/devices (e.g., such as UE 120 c) wearable devices (smartwatches, smart clothing, smart glasses, smart wrist bands, smart jewelry(e.g., smart ring, smart bracelet)), an entertainment device (e.g., amusic or video device, or a satellite radio), a vehicular component orsensor, smart meters/sensors, industrial manufacturing equipment, aglobal positioning system device, a smart home device (e.g., a smartappliance, a smart light bulb, and/or the like, such as UE 120 a), orany other suitable device that is configured to communicate via awireless or wired medium.

Some UEs may be considered machine-type communication (MTC) or evolvedor enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEsinclude, for example, robots, drones, remote devices, such as sensors,meters, monitors, location tags, etc., that may communicate with a basestation, another device (e.g., remote device), or some other entity. Awireless node may provide, for example, connectivity for or to a network(e.g., a wide area network such as Internet or a cellular network) via awired or wireless communication link. Some UEs may be considered IoTdevices, and/or may be implemented as may be implemented as NB-IoTdevices. Some UEs may be considered a Customer Premises Equipment (CPE).UE 120 may be included inside a housing that houses components of UE120, such as processor components, memory components, and/or the like.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular RAT andmay operate on one or more frequencies. A RAT may also be referred to asa radio technology, an air interface, and/or the like. A frequency mayalso be referred to as a carrier, a frequency channel, and/or the like.Each frequency may support a single RAT in a given geographic area inorder to avoid interference between wireless networks of different RATs.In some cases, 5G RAT networks may be deployed.

In some examples, access to the air interface may be scheduled, whereina scheduling entity (e.g., a base station) allocates resources forcommunication among some or all devices and equipment within thescheduling entity's service area or cell. Within the present disclosure,as discussed further below, the scheduling entity may be responsible forscheduling, assigning, reconfiguring, and releasing resources for one ormore subordinate entities. That is, for scheduled communication,subordinate entities utilize resources allocated by the schedulingentity.

Base stations are not the only entities that may function as ascheduling entity. That is, in some examples, a UE may function as ascheduling entity, scheduling resources for one or more subordinateentities (e.g., one or more other UEs). In this example, the UE isfunctioning as a scheduling entity, and other UEs utilize resourcesscheduled by the UE for wireless communication. A UE may function as ascheduling entity in a peer-to-peer (P2P) network, and/or in a meshnetwork. In a mesh network example, UEs may optionally communicatedirectly with one another in addition to communicating with thescheduling entity.

Thus, in a wireless communication network with a scheduled access totime-frequency resources and having a cellular configuration, a P2Pconfiguration, and a mesh configuration, a scheduling entity and one ormore subordinate entities may communicate utilizing the scheduledresources.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 1.

FIG. 2 shows a block diagram 200 of a design of base station 110 and UE120, which may be one of the base stations and one of the UEs in FIG. 1.Base station 110 may be equipped with T antennas 234 a through 234 t,and UE 120 may be equipped with R antennas 252 a through 252 r, where ingeneral T≥1 and R≥1.

At base station 110, a transmit processor 220 may receive data from adata source 212 for one or more UEs, select one or more modulation andcoding schemes (MCS) for each UE based at least in part on channelquality indicators (CQIs) received from the UE, process (e.g., encodeand modulate) the data for each UE based at least in part on the MCS(s)selected for the UE, and provide data symbols for all UEs. Transmitprocessor 220 may also process system information (e.g., for semi-staticresource partitioning information (SRPI), and/or the like) and controlinformation (e.g., CQI requests, grants, upper layer signaling, and/orthe like) and provide overhead symbols and control symbols. Transmitprocessor 220 may also generate reference symbols for reference signals(e.g., the CRS) and synchronization signals (e.g., the primarysynchronization signal (PSS) and secondary synchronization signal(SSS)). For example, transmit processor 220 may generate referencesymbols associated with a system information block (SIB) message fortransmission on a non-anchor carrier. A transmit (TX) multiple-inputmultiple-output (MIMO) processor 230 may perform spatial processing(e.g., precoding) on the data symbols, the control symbols, the overheadsymbols, and/or the reference symbols, if applicable, and may provide Toutput symbol streams to T modulators (MODs) 232 a through 232 t. Eachmodulator 232 may process a respective output symbol stream (e.g., forOFDM and/or the like) to obtain an output sample stream. Each modulator232 may further process (e.g., convert to analog, amplify, filter, andupconvert) the output sample stream to obtain a downlink signal. Tdownlink signals from modulators 232 a through 232 t may be transmittedvia T antennas 234 a through 234 t, respectively. According to variousaspects described in more detail below, the synchronization signals canbe generated with location encoding to convey additional information.

At UE 120, antennas 252 a through 252 r may receive the downlink signalsfrom base station 110 and/or other base stations and may providereceived signals to demodulators (DEMODs) 254 a through 254 r,respectively. Each demodulator 254 may condition (e.g., filter, amplify,downconvert, and digitize) a received signal to obtain input samples.Each demodulator 254 may further process the input samples (e.g., forOFDM and/or the like) to obtain received symbols. A MIMO detector 256may obtain received symbols from all R demodulators 254 a through 254 r,perform MIMO detection on the received symbols if applicable, andprovide detected symbols. A receive (RX) processor 258 may process(e.g., demodulate and decode) the detected symbols, provide decoded datafor UE 120 to a data sink 260, and provide decoded control informationand system information to a controller/processor 280. A channelprocessor may determine RSRP, RSSI, RSRQ, CQI, and/or the like.

On the uplink, at UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports comprising RSRP, RSSI, RSRQ, CQI, and/or the like) fromcontroller/processor 280. For example, transmit processor 264 mayprocess data, such as data identifying a plurality of carriers, toenable transmission of a connection request message using a carrier ofthe plurality of carriers, such as an anchor carrier, a non-anchorcarrier, and/or the like. Transmit processor 264 may also generatereference symbols for one or more reference signals. The symbols fromtransmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by modulators 254 a through 254 r (e.g.,for DFT-s-OFDM, CP-OFDM, and/or the like), and transmitted to basestation 110. At base station 110, the uplink signals from UE 120 andother UEs may be received by antennas 234, processed by demodulators232, detected by a MIMO detector 236 if applicable, and furtherprocessed by a receive processor 238 to obtain decoded data and controlinformation sent by UE 120. Receive processor 238 may provide thedecoded data to a data sink 239 and the decoded control information tocontroller/processor 240. Base station 110 may include communicationunit 244 and communicate to network controller 130 via communicationunit 244. Network controller 130 may include communication unit 294,controller/processor 290, and memory 292.

Controller/processor 240 of base station 110, controller/processor 280of UE 120, and/or any other component(s) of FIG. 2 may perform one ormore techniques associated with carrier management, as described in moredetail elsewhere herein. For example, controller/processor 240 of basestation 110, controller/processor 280 of UE 120, and/or any othercomponent(s) of FIG. 2 may perform or direct operations of, for example,method 1000 of FIG. 10, method 1300 of FIG. 13, and/or other processesas described herein. Memories 242 and 282 may store data and programcodes for BS 110 and UE 120, respectively. A scheduler 246 may scheduleUEs for data transmission on the downlink and/or uplink.

As indicated above, FIG. 2 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 2.

5G may refer to radios configured to operate according to a new airinterface (e.g., other than Orthogonal Frequency Divisional MultipleAccess (OFDMA)-based air interfaces) or fixed transport layer (e.g.,other than Internet Protocol (IP)). In aspects, 5G may utilize OFDM witha CP (herein referred to as cyclic prefix OFDM or CP-OFDM) and/or SC-FDMon the uplink, may utilize CP-OFDM on the downlink and include supportfor half-duplex operation using TDD. In aspects, 5G may, for example,utilize OFDM with a CP (herein referred to as CP-OFDM) and/or discreteFourier transform spread orthogonal frequency-division multiplexing(DFT-s-OFDM) on the uplink, may utilize CP-OFDM on the downlink andinclude support for half-duplex operation using TDD. 5G may includeEnhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g.,80 megahertz (MHz) and beyond), millimeter wave (mmW) targeting highcarrier frequency (e.g., 60 gigahertz (GHz)), massive MTC (mMTC)targeting non-backward compatible MTC techniques, and/or missioncritical targeting ultra reliable low latency communications (URLLC)service.

A single component carrier bandwidth of 100 MHZ may be supported. 5Gresource blocks may span 12 sub-carriers with a sub-carrier bandwidth of75 kilohertz (kHz) over a 0.1 ms duration. Each radio frame may include50 subframes with a length of 10 ms. Consequently, each subframe mayhave a length of 0.2 ms. Each subframe may indicate a link direction(e.g., DL or UL) for data transmission and the link direction for eachsubframe may be dynamically switched. Each subframe may include DL/ULdata as well as DL/UL control data.

Beamforming may be supported and beam direction may be dynamicallyconfigured. MIMO transmissions with precoding may also be supported.MIMO configurations in the DL may support up to 8 transmit antennas withmulti-layer DL transmissions up to 8 streams and up to 2 streams per UE.Multi-layer transmissions with up to 2 streams per UE may be supported.Aggregation of multiple cells may be supported with up to 8 servingcells. Alternatively, 5G may support a different air interface, otherthan an OFDM-based interface. 5G networks may include entities suchcentral units or distributed units.

The RAN may include a central unit (CU) and distributed units (DUs). A5G BS (e.g., gNB, 5G Node B, Node B, transmit receive point (TRP),access point (AP)) may correspond to one or multiple BSs. 5G cells canbe configured as access cells (ACells) or data only cells (DCells). Forexample, the RAN (e.g., a central unit or distributed unit) canconfigure the cells. DCells may be cells used for carrier aggregation ordual connectivity, but not used for initial access, cellselection/reselection, or handover. In some aspects, DCells may nottransmit synchronization signals. In some aspects, DCells may transmitsynchronization signals. 5G BSs may transmit downlink signals to UEsindicating the cell type. Based at least in part on the cell typeindication, the UE may communicate with the 5G BS. For example, the UEmay determine 5G BSs to consider for cell selection, access, handover,and/or measurement based at least in part on the indicated cell type.

FIG. 3 illustrates an example logical architecture of a distributed RAN300, according to aspects of the present disclosure. A 5G access node306 may include an access node controller (ANC) 302. The ANC may be acentral unit (CU) of the distributed RAN 300. The backhaul interface tothe next generation core network (NG-CN) 304 may terminate at the ANC.The backhaul interface to neighboring next generation access nodes(NG-ANs) may terminate at the ANC. The ANC may include one or more TRPs308 (which may also be referred to as BSs, 5G BSs, Node Bs, 5G NBs, APs,gNB, or some other term). As described above, a TRP may be usedinterchangeably with “cell.”

The TRPs 308 may be a distributed unit (DU). The TRPs may be connectedto one ANC (ANC 302) or more than one ANC (not illustrated). Forexample, for RAN sharing, radio as a service (RaaS), and servicespecific AND deployments, the TRP may be connected to more than one ANC.A TRP may include one or more antenna ports. The TRPs may be configuredto individually (e.g., dynamic selection) or jointly (e.g., jointtransmission) serve traffic to a UE.

The local architecture of RAN 300 may be used to illustrate fronthauldefinition. The architecture may be defined that support fronthaulingsolutions across different deployment types. For example, thearchitecture may be based at least in part on transmit networkcapabilities (e.g., bandwidth, latency, and/or jitter).

The architecture may share features and/or components with LTE.According to aspects, the next generation AN (NG-AN) 310 may supportdual connectivity with 5G. The NG-AN may share a common fronthaul forLTE and 5G.

The architecture may enable cooperation between and among TRPs 308. Forexample, cooperation may be preset within a TRP and/or across TRPs viathe ANC 302. According to aspects, no inter-TRP interface may beneeded/present.

According to aspects, a dynamic configuration of split logical functionsmay be present within the architecture of RAN 300. The PDCP, RLC, MACprotocol may be adaptably placed at the ANC or TRP.

According to various aspects, a BS may include a central unit (CU)(e.g., ANC 302) and/or one or more distributed units (e.g., one or moreTRPs 308).

As indicated above, FIG. 3 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 3.

FIG. 4 illustrates an example physical architecture of a distributed RAN400, according to aspects of the present disclosure. A centralized corenetwork unit (C-CU) 402 may host core network functions. The C-CU may becentrally deployed. C-CU functionality may be offloaded (e.g., toadvanced wireless services (AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 404 may host one or more ANC functions.Optionally, the C-RU may host core network functions locally. The C-RUmay have distributed deployment. The C-RU may be closer to the networkedge.

A distributed unit (DU) 406 may host one or more TRPs. The DU may belocated at edges of the network with radio frequency (RF) functionality.

As indicated above, FIG. 4 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 4.

FIG. 5 is a diagram illustrating an example 500 relating to carriermanagement for transmitting the SIB1-NB on the non-anchor carrier forNB-IoT inband deployment mode.

At 510, a base station (e.g., BS 110) may determine a frequency domainlocation for the anchor carrier from a plurality of potential frequencydomain locations. For example, the base station may determine, based atleast in part on stored information, the plurality of potentialfrequency domain locations for the anchor carrier.

At 520, the base station may determine a center frequency for an inbandcommunication system (e.g., an LTE communication system).

At 530, the base station may identify an offset index value for theanchor carrier relative to the center frequency. In some aspects, theoffset index value may be a physical resource block (PRB) index offset,P, for the anchor carrier relative to the center frequency. The basestation may signal the index offset in a master information block (MIB)to enable a UE (e.g., UE 120) to determine the frequency location of theanchor carrier after decoding the MIB. In some aspects, the MIB mayinclude a 1-bit indicator to indicate the frequency location, such asindicating a PRB adjacent to and at a lower frequency range than thecenter frequency or a PRB adjacent to and at a higher frequency rangethan the center frequency.

At 540, the base station may select, for a non-anchor carrier, anotherfrequency domain location, such that the non-anchor carrier is at anopposite PRB to the anchor carrier relative to a center frequencyposition. For example, the base station may determine that a physicalresource block index offset for the non-anchor carrier is an inverse ofa physical resource block index offset for the anchor carrier. In otherwords, for an anchor carrier physical resource block index offset, P,the non-anchor carrier physical resource block index offset is P. Inthis way, the base station obviates a need to transmit information tosignal the frequency location of the non-anchor carrier for SIB-NB,thereby reducing utilization of network resources. The UE may determinea frequency domain location parameter identifying a frequency domainlocation of the non-anchor carrier based at least in part on the offsetindex of the anchor carrier, thereby reducing utilization of networkresources relative to requiring separate messages to signal thefrequency domain location of the anchor carrier and the frequency domainlocation of the non-anchor carrier.

As indicated above, FIG. 5 is provided as an example. Other examples arepossible and may differ from what was described with respect to FIG. 5.

FIG. 6 is a diagram illustrating an example 600 relating to carriermanagement.

At 610, a base station (e.g., BS 110) may determine to provide an anchorcarrier and a non-anchor carrier in a common resource block group. Forexample, in an LTE communications system with a 10 megahertz (MHz)bandwidth, the base station may determine to use a physical resourceblock (PRB) with index 9 for an anchor carrier, and physical resourceblocks with indices 10 and/or 11 for a non-anchor carrier. In this case,the physical resource blocks of the anchor carrier and the non-anchorcarrier are included in a single resource block group of index 3 (RGB3),where the physical resource blocks for the non-anchor carrier (PRB 9)follow the physical resource block for the anchor carrier with aphysical resource block offset value of 1 and/or 2 (PRB 10 and/or 11).

At 620, similarly, the base station may determine to use physicalresource blocks with indices 33 and/or 34 for a non-anchor carrier and aphysical resource block 35 for an anchor carrier. In this case, thephysical resource blocks of the non-anchor carrier and the anchorcarrier are included in a single resource block group of index 11 (RGB11), where the physical resource block (PRB 35) for the non-anchorcarrier follows the physical resource blocks for the anchor carrier withan offset value of −1 and/or −2 (PRB 34 and/or 33). In some aspects, oneof a set of four physical resource block offset index values may besignaled to the UE using a two bit indicator, and the UE may identifythe frequency of an non-anchor carrier based at least in part on theoffset index value that is signaled. In this way, a degradation ofphysical resource block group utilization is reduced based at least inpart on reducing a likelihood of misalignment of the carriers and theresource block groups for the inband LTE communication system.

As indicated above, FIG. 6 is provided as an example. Other examples arepossible and may differ from what was described with respect to FIG. 6.

FIG. 7 is a diagram illustrating an example 700 relating to carriermanagement for SIB1-NB on both an anchor and non-anchor carrier.

At 710, at least one base station (e.g., BS 110) may provide a pluralityof cells for a SIB1-NB transmission. In some aspects, the SIB1-NB may beassociated with a particular period, such as a 2560 millisecond (ms)period, which may be portioned into 160 ms increments for anchorcarriers and non-anchor carriers with a transmission time interval (TTI)length of 80 ms for a SIB1-NB transmission. In some aspects, the SIB1-NBmay be transmitted in a particular subframe of a particular radio frame,such as subframe 0 of alternating radio frames (e.g., subframe 0 ofradio frames 1, 3, 5, etc. or of radio frames 2, 4, 6, 8, etc.), whentransmitted on an anchor carrier. Additionally, or alternatively, whentransmitted on a non-anchor carrier, the SIB1-NB may be transmitted onsubframes 0 and 5 of alternating radio frames (e.g., subframe 0 and 5 ofradio frames 1, 3, 5, etc. or of radio frames 2, 4, 6, 8, etc.).

At 720, the base station may transmit an anchor carrier and/or anon-anchor carrier via one or more cells of the plurality of cells. Insome aspects, the base station may determine a power boosting parameterfor transmissions of the anchor carrier and/or the non-anchor carrier.For example, for an inband operation mode or a guard band operation modewith a common power amplifier for physical resource blocks of a carrier,a power boosting for a non-anchor carrier for the SIB1-NB transmissionmay be 3 decibels (dB). In contrast, a power boosting for an anchorcarrier may be 6 dB. As a result, the base station may assign a greaterquantity of subframes for transmission of a SIB1-NB on the non-anchorcarrier relative to a quantity of subframes for transmission of theSIB1-NB on the anchor carrier. For example, the base station maytransmit the SIB1-NB in each subframe of index 0 and subframe of index 5in alternating radio frames on the non-anchor carrier, and may transmitthe SIB1-NB in each subframe of index 0 in alternating radio frames onthe anchor carrier. In this case, the base station may transmit 16repetitions of the SIB1-NB on the non-anchor carrier or 8 repetitions ofthe SIB1-NB on the anchor carrier. In some aspects, the base station maytransmit the SIB1-NB on both the anchor carrier and the non-anchorcarrier. For example, the base station may transmit one SIB1-NBrepetition on the anchor carrier and two SIB1-NB repetitions on thenon-anchor carrier.

In some aspects, the non-anchor carrier may be adjacent to the anchorcarrier in a common guard band. In some aspects, the non-anchor carriermay at a frequency location opposite the anchor carrier in a guard band.In some aspects, the non-anchor carrier may be in an inband physicalresource block (PRB) adjacent to the anchor carrier.

As indicated above, FIG. 7 is provided as an example. Other examples arepossible and may differ from what was described with respect to FIG. 7.

FIG. 8 is a diagram illustrating an example 800 relating to carriermanagement for SIB1-NB on a non-anchor carrier.

As shown in FIG. 8, a base station (e.g., BS 110) may provide a SIB1-NBin a guard band operation mode with a plurality of power amplifiers orin a standalone mode. For example, the base station may provide theSIB1-NB with a common power boosting parameter for an anchor carrier anda non-anchor carrier. In this case, a quantity of subframes and framesfor the SIB1-NB transmission can be common to the anchor carrier and thenon-anchor carrier.

At 810 and 820, the base station may provide a set of 4 repetitions of aSIB1-NB transmission in each 2560 ms SIB1-NB period and using a carrierlength of 160 ms. In this case, the base station may determine a frameoffset of 0 ms, 160 ms, 320 ms, 480 ms, given the 2560 ms period. Insome aspects, the base station may provide a SIB1-NB transmission in a10 ms period of each 160 ms period within a carrier.

At 830 and 840, in contrast, the base station may provide a set of 8repetitions of a SIB1-NB transmission in each 2560 ms period. In thiscase, the base station may determine a frame offset of 0 ms or 160 ms.In some aspects, the base station may transmit the SIB1-NB in subframe 0of alternating radio frames. For example, the base station may selectbetween transmitting in odd indexed radio frames or even indexed radioframes based at least in part on a cell identifier associated with acell, a quantity of repetitions per SIB1-NB period, and/or the like. Inthis case, as shown, the base station may determine to transmit a firstSIB1-NB for a cell with an even physical cell identity value (PCID) anda second SIB1-NB for a cell with an odd physical cell identity value inalternating portions of the SIB1-NB period.

As indicated above, FIG. 8 is provided as an example. Other examples arepossible and may differ from what was described with respect to FIG. 8.

FIG. 9 is a diagram illustrating an example 900 relating to carriermanagement for transmitting a random access message.

At 910, for a frequency division duplex (FDD) NB-IoT communicationssystem, a user equipment (e.g., UE 120) may transmit a narrowbandphysical random access channel (NB-PRACH or NPRACH) and a connectionrequest message (e.g., a Msg3 type message using a physical uplinkshared channel PUSCH) on a common carrier. For example, the userequipment may transmit a 180 kilohertz (KHz) band channel with aparticular NB-PRACH periodicity and with a first portion allocated forthe NB-PRACH transmission and a second portion available for aconnection request message. In some aspects, when a collision occurs forthe NB-PRACH transmission and the connection request message, the userequipment may postpone transmission of the connection request message toa later uplink subframe not overlapping with an NB-PRACH resource.

At 920, for a time division duplex (TDD) NB-IoT communications system,the user equipment may transmit an NB-PRACH and a connection requestmessage on one or more carriers. In some aspects, UE 120 may transmitthe random access channel and the connection request message using acommon carrier. In this case, postponing transmission of the connectionrequest message may cause excessive delay as a result of less than athreshold quantity of uplink subframes being allocated for the userequipment, such as in a downlink-favored configuration. For example, inTDD configuration type 2, the user equipment may be allocated two uplinksubframes in each frame and the NB-PRACH may be transmitted in portionsof both of the two uplink subframes. In some aspects, the user equipmentmay permit the connection request message and the NB-PRACH to betransmitted on different carriers rather than on a common carrier aswith FDD NB-IoT. In some aspects, UE 120 may transmit the random accesschannel using a first carrier and the connection request message using asecond carrier that is different from the first carrier. For example,based at least in part on receiving a bit indicator in a random accessresponse (RAR) message or in a system information block message, theuser equipment may identify a plurality of carriers, such as twonon-anchor carriers, an anchor carrier and a non-anchor carrier, and/orthe like. In this case, the user equipment may transmit the NB-PRACH ona first carrier of the plurality of carriers (e.g., the anchor carrieror a non-anchor carrier of a plurality of non-anchor carriers) and theconnection request message on the second carrier of the plurality ofcarriers (e.g., on a non-anchor carrier).

In some aspects, the user equipment may receive a message indicatingdifferent carriers for the NB-PRACH and the connection request message,and may determine whether to transmit the NB-PRACH and the connectionrequest message on the different carriers based at least in part onwhether the NB-PRACH can be multiplexed with the connection requestmessage in a single physical resource block. For example, the userequipment may determine whether to transmit the NB-PRACH and theconnection request message in the different carriers based at least inpart on a quantity of NB-PRACH subcarriers, a transmission bandwidth forthe connection request message, and/or the like.

As indicated above, FIG. 9 is provided as an example. Other examples arepossible and may differ from what was described with respect to FIG. 9.

FIG. 10 is a flow chart of a method 1000 of wireless communication fortransmitting the SIB1-NB on the non-anchor carrier. The method may beperformed by a base station (e.g., the BS 110, the apparatus 1102/1102′,the BS 1450, and/or the like).

At 1010, in some aspects, the base station may determine a plurality ofparameters for a non-anchor carrier or an anchor carrier. For example,the base station (e.g., using controller/processor 240 and/or the like)may determine a plurality of parameters for at least one of a non-anchorcarrier or an anchor carrier, wherein the plurality of parametersinclude a frequency domain location parameter and a time domain locationparameter.

At 1020, the base station may transmit a master information blockmessage identifying the plurality of parameters. For example, the basestation (e.g., using controller/processor 240, transmit processor 220,TX MIMO processor 230, MOD 232, antenna 234, and/or the like) maytransmit a master information block message that identifies a frequencydomain location parameter, a time domain location parameter, and/or thelike.

At 1030, the base station may transmit the system information block type1 (SIB1) message. For example, the base station (e.g., usingcontroller/processor 240, transmit processor 220, TX MIMO processor 230,MOD 232, antenna 234, and/or the like) may transmit, using thenon-anchor carrier or the anchor carrier, SIB1 message to a userequipment in accordance with a frequency domain location parameter, atime domain location parameter, and/or the like. In some aspects, thebase station may generate the SIB1 message for NB-IoT communicationswith the user equipment. In some aspects, the SIB1 message may beanother type of message, such as another type of system informationblock message, a non-system information block message, and/or the like.

Method 1000 may include additional aspects, such as any single aspect orany combination of aspects described below.

In some aspects, the SIB1 message is transmitted in a subframe 0 and asubframe 5 of alternating radio frames of the non-anchor carrier. Insome aspects, the SIB1 message is transmitted in a subframe 0 ofalternating radio frames of the anchor carrier. In some aspects, thefrequency domain location parameter is identifies associated with aphysical resource block offset relative to a center frequency, and theanchor carrier is in a first frequency range greater than the centerfrequency by the physical resource block offset and the non-anchorcarrier is in a second frequency range less than the center frequency bythe physical resource block offset, or the non-anchor carrier is in thefirst frequency range greater than the center frequency by the physicalresource block offset and the anchor carrier is in the second frequencyrange less than the center frequency by the physical resource blockoffset.

In some aspects, the non-anchor carrier is in at least one firstphysical resource block, of a resource block group, and the non-anchorcarrier is in at least one second physical resource block, of theresource block group, that is contiguous to the at least one firstphysical resource block without one or more physical resource blocks, ofthe resource block group, between the at least one first physicalresource block and the at least one second physical resource block. Insome aspects, the non-anchor carrier and the anchor carrier areassociated with a common guard band. In some aspects, the at least onesecond physical resource block is an inband physical resource block. Insome aspects, the non-anchor carrier is in a first guardband and theanchor carrier is in a second guardband that is different than the firstguardband.

In some aspects, a size or a value for the indicator at least oneparameter, of the plurality of parameters, is identified based at leastin part on a deployment mode, the deployment mode is at least one of:operation in one of an in-band deployment mode, a guard band deploymentmode, or a stand-alone deployment mode. In some aspects, the frequencydomain location parameter or the time domain location parameter is basedat least in part on an offset indicator identifying a resource blockoffset with respect to the anchor carrier. In some aspects, the offsetindicator is based at least in part on a resource block group, and theanchor carrier and the non-anchor carrier are in resource blocks of theresource block group. In some aspects, a frequency domain location forthe non-anchor carrier is opposite a frequency domain location of theanchor carrier with respect to a center frequency.

In some aspects, at least one parameter, of the plurality of parameters,is identified based at least in part on a physical resource block indexoffset of an anchor carrier. In some aspects, at least one parameter, ofthe plurality of parameters, is identified based at least in part on aresource block group of an inband communication. In some aspects, atleast one repetition of the SIB1 message is transmitted on an anchorcarrier and at least one repetition of the SIB1 message is transmittedon the non-anchor carrier.

In some aspects, a power boosting parameter, of the plurality ofparameters, for the non-anchor carrier is less than a power value forthe anchor carrier. In some aspects, a quantity of repetitions of atransmission on the non-anchor carrier is greater than a quantity ofrepetitions of a transmission on the anchor carrier. In some aspects, asubframe or frame for the SIB1 message is determined based at least inpart on a cell identifier or a repetition configuration.

Although FIG. 10 shows example blocks of a method of wirelesscommunication, in some aspects, the method may include additionalblocks, fewer blocks, different blocks, or differently arranged blocksthan those shown in FIG. 10. Additionally, or alternatively, two or moreblocks shown in FIG. 10 may be performed in parallel.

FIG. 11 is a conceptual data flow diagram 1100 illustrating the dataflow between different modules/means/components in an example apparatus1102. The apparatus 1102 may be a BS. In some aspects, the apparatus1102 includes a reception module 1104, a determining module 1106, and/ora transmission module 1108.

The reception module 1104 may receive, from a user equipment 1150 and asdata 1110 information associated with an NB-IoT communication. In someaspects, the reception module 1104 may receive a master informationblock message. For example, the reception module 1104 may receive amaster information block message including a group of bits to signal anNB-IoT carrier frequency.

The determining module 1106 may receive, from the reception module 1104and as data 1112 information associated with determining a plurality ofparameters for an NB-IoT communication. In some aspects, the determiningmodule 1106 may determine a plurality of parameters for a non-anchorcarrier of a plurality of carriers. For example, the determining module1106 may determine a frequency domain location parameter, a time domainlocation parameter, and/or the like for the non-anchor carrier. In someaspects, the determining module 1106 may determine the plurality ofparameters based at least in part on information of a master informationblock message. For example, the determining module 1106 may determine afrequency location of the non-anchor carrier based at least in part on agroup of bits included in a master information block message.

In some aspects, the determining module 1106 may determine a parameter,of the plurality of parameters, based at least in part on a deploymentmode for NB-IoT. For example, for an in-band deployment mode, thedetermining module 1106 may determine that 5 bits of the masterinformation block message indicate a physical resource block indexoffset value identifying an offset of the non-anchor carrier or ananchor carrier from a central frequency of a communications system. Inthis case, the offset of the non-anchor carrier may be an inverse of anoffset of the anchor carrier. Additionally, or alternatively, for aguard band deployment or an in-band deployment, the master informationblock may include 2 bits associated with identifying a physical resourceblock index offset of a group of four configured physical resource blockindex offsets. In some aspects, the determining module 1106 maydetermine a parameter, of the plurality of parameters, based at least inpart on a resource block group of an anchor carrier. For example, thedetermining module 1106 may determine a resource block group of theanchor carrier and may determine a frequency location and/or a timelocation of the non-anchor carrier, such that the non-anchor carrier isin the same resource block group.

In some aspects, the determining module 1106 may determine a powerboosting parameter, of the plurality of parameters, for the non-anchorcarrier. For example, the determining module 1106 may determine that thenon-anchor carrier is to be associated with a lesser power value thanfor the anchor carrier. Additionally, or alternatively, the determiningmodule 1106 may determine that the non-anchor carrier and the anchorcarrier are to be associated with a common power value.

The transmission module 1108 may receive, from the determining module1106 and as data 1114, information associated with transmitting data1116 to the user equipment 1150. In some aspects, the transmissionmodule 1108 may transmit a master information block message to identifya plurality of parameters associated with a system information blockmessage (e.g., a time domain location parameter, a frequency domainlocation parameter, and/or the like). In some aspects, the transmissionmodule 1108 may transmit repetitions of a system information blockmessage to the user equipment 1150. For example, the transmission module1108 may transmit multiple repetitions on an anchor carrier, on thenon-anchor carrier, on a combination of the anchor carrier and thenon-anchor carrier, and/or the like. In some aspects, the transmissionmodule 1108 may transmit a particular quantity of repetitions of thesystem information block message. For example, when transmitting on thenon-anchor carrier with a lesser power boosting value, the transmissionmodule 1108 may transmit a greater quantity of repetitions on thenon-anchor carrier relative to when transmitting on the anchor carrierwith a greater power boosting value. In some aspects, the transmissionmodule 1108 may transmit using a particular subset of resources, such asa particular subset of subframes or frames. For example, thetransmission module 1108 may transmit using a particular subframe orframe based at least in part on a cell identifier for a cell, arepetition configuration (e.g., a quantity of configured repetitions),and/or the like.

The apparatus may include additional modules that perform each of theblocks of the algorithm in the aforementioned flow chart of FIG. 10. Assuch, each block in the aforementioned flow chart of FIG. 10 may beperformed by a module and the apparatus may include one or more of thosemodules. The modules may be one or more hardware components specificallyconfigured to carry out the stated processes/algorithm, implemented by aprocessor configured to perform the stated processes/algorithm, storedwithin a computer-readable medium for implementation by a processor, orsome combination thereof.

The number and arrangement of modules shown in FIG. 11 are provided asan example. In practice, there may be additional modules, fewer modules,different modules, or differently arranged modules than those shown inFIG. 11. Furthermore, two or more modules shown in FIG. 11 may beimplemented within a single module, or a single module shown in FIG. 11may be implemented as multiple, distributed modules. Additionally, oralternatively, a set of modules (e.g., one or more modules) shown inFIG. 11 may perform one or more functions described as being performedby another set of modules shown in FIG. 11.

FIG. 12 is a diagram 1200 illustrating an example of a hardwareimplementation for an apparatus 1102′ employing a processing system1202. The apparatus 1102′ may be a BS.

The processing system 1202 may be implemented with a bus architecture,represented generally by the bus 1204. The bus 1204 may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system 1202 and the overall designconstraints. The bus 1204 links together various circuits including oneor more processors and/or hardware modules, represented by the processor1206, the modules 1104, 1106, 1108, and the computer-readablemedium/memory 1208. The bus 1204 may also link various other circuitssuch as timing sources, peripherals, voltage regulators, and powermanagement circuits, which are well known in the art, and therefore,will not be described any further.

The processing system 1202 may be coupled to a transceiver 1210. Thetransceiver 1210 is coupled to one or more antennas 1212. Thetransceiver 1210 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1210 receives asignal from the one or more antennas 1212, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1202, specifically the reception module 1104. Inaddition, the transceiver 1210 receives information from the processingsystem 1202, specifically the transmission module 1108, and based atleast in part on the received information, generates a signal to beapplied to the one or more antennas 1212. The processing system 1202includes a processor 1206 coupled to a computer-readable medium/memory1208. The processor 1206 is responsible for general processing,including the execution of software stored on the computer-readablemedium/memory 1208. The software, when executed by the processor 1206,causes the processing system 1202 to perform the various functionsdescribed supra for any particular apparatus. The computer-readablemedium/memory 1208 may also be used for storing data that is manipulatedby the processor 1206 when executing software. The processing systemfurther includes at least one of the modules 1104, 1106, and 1108. Themodules may be software modules running in the processor 1206,resident/stored in the computer readable medium/memory 1208, one or morehardware modules coupled to the processor 1206, or some combinationthereof. The processing system 1202 may be a component of the BS 110 andmay include the memory 242 and/or at least one of the TX MIMO processor230, the RX processor 238, and/or the controller/processor 240.

In some aspects, the apparatus 1102/1102′ for wireless communicationincludes means for transmitting a master information block messageincluding an indicator identifying a frequency domain location parameteror a time domain location parameter for a non-anchor carrier or ananchor carrier, means for transmitting, using the non-anchor carrier orthe anchor carrier, a system information block type 1 (SIB1) message toa user equipment in accordance with the frequency domain locationparameter or the time domain location parameter, and/or the like. Theaforementioned means may be one or more of the aforementioned modules ofthe apparatus 1102 and/or the processing system 1202 of the apparatus1102′ configured to perform the functions recited by the aforementionedmeans. As described supra, the processing system 1202 may include the TXMIMO processor 230, the receive processor 238, and/or thecontroller/processor 240. As such, in one configuration, theaforementioned means may be the TX MIMO processor 230, the receiveprocessor 238, and/or the controller/processor 240 configured to performthe functions recited by the aforementioned means.

FIG. 12 is provided as an example. Other examples are possible and maydiffer from what was described in connection with FIG. 12.

FIG. 13 is a flow chart of a method 1300 of wireless communication fortransmitting a connection request message. The method may be performedby a user equipment (e.g., the UE 120, the UE 1150, the apparatus1402/1402′, and/or the like).

At 1310, in some aspects, the user equipment may identify a plurality ofcarriers. For example, the user equipment (e.g., usingcontroller/processor 280 and/or the like) may identify a plurality ofcarriers in a time division duplex network for random access.

At 1320, the user equipment may transmit a random access channel using afirst carrier of the plurality of carriers. For example, the userequipment (e.g., using controller/processor 280, transmit processor 264,TX MIMO processor 266, MOD 254, antenna 252, and/or the like) maytransmit a random access channel preamble using a first carrier, of theplurality of carriers, based at least in part on identifying theplurality of carriers.

At 1330, the user equipment may transmit a connection request messageusing a second carrier of the plurality of carriers. For example, theuser equipment (e.g., using controller/processor 280, transmit processor264, TX MIMO processor 266, MOD 254, antenna 252, and/or the like) maytransmit a connection request message using a second carrier, of theplurality of carriers, that is different from the first carrier.

Method 1300 may include additional aspects, such as any single aspect orany combination of aspects described below.

In some aspects, the plurality of carriers include at least one anchorcarrier and at least one non-anchor carrier used for a random accesschannel message. In some aspects, the second carrier for the connectionrequest message is based at least in part on a carrier selectionindicator from a random access response message (msg2).

In some aspects, the second carrier for the connection request messageis based at least in part on predetermined information or a receivedsystem information block message. In some aspects, the connectionrequest message is transmitted using a next available subframe notoverlapping with a random access channel resource. In some aspects, atleast one of the plurality of carriers is based at least in part on acarrier selection indicator of a random access message.

In some aspects, the plurality of carriers includes another non-anchorcarrier or an anchor carrier. In some aspects, the connection requestmessage and the random access channel message are multiplexed in acommon resource block. In some aspects, the second carrier for theconnection request message is selected based at least in part on aquantity of random access channel subcarriers and a transmissionbandwidth associated with the connection request message.

In some aspects, the connection request message and the random accesschannel message are transmitted using a common carrier of the pluralityof carriers. In some aspects, the plurality of carriers are identifiedbased at least in part on stored information or a received systeminformation block message. In some aspects, the connection requestmessage is transmitted using a next available subframe not overlappingwith a random access channel resource.

Although FIG. 13 shows example blocks of a method of wirelesscommunication, in some aspects, the method may include additionalblocks, fewer blocks, different blocks, or differently arranged blocksthan those shown in FIG. 13. Additionally, or alternatively, two or moreblocks shown in FIG. 13 may be performed in parallel.

FIG. 14 is a conceptual data flow diagram 1400 illustrating the dataflow between different modules/means/components in an example apparatus1402. The apparatus 1402 may be a UE. In some aspects, the apparatus1402 includes a reception module 1404, an identifying module 1406,and/or a transmission module 1408.

The reception module 1404 may receive, from a base station 1450 and asdata 1410, information associated with identifying a plurality ofcarriers. In some aspects, the reception module 1404 may receive acarrier selection indicator. For example, the reception module 1404 mayreceive a random access request message with a bit indicator identifyinga different carrier (e.g., different relative to a carrier fortransmitting the NB-PRACH) for transmitting a connection request message(e.g., a Msg3 type message). Additionally, or alternatively, thereception module 1404 may receive a system information block messageidentifying the different carrier.

The identifying module 1406 may receive, from the reception module 1404and as data 1412, information associated with identifying the pluralityof carriers. Additionally, or alternatively, the identifying module 1406may identify the plurality of carriers based at least in part on astored configuration. In some aspects, the identifying module 1406 mayidentify the plurality of carriers in a time division duplex network.For example, the identifying module 1406 may identify a non-anchorcarrier for a connection request message and an anchor carrier for anNB-PRACH message. In some aspects, the identifying module 1406 mayidentify a carrier for transmitting a connection request message basedat least in part on a received carrier selection indicator.

In some aspects, the identifying module 1406 may identify a carrier forthe connection request message based at least in part on acharacteristic of the NB-PRACH. For example, based at least in part onthe connection request message and the NB-PRACH being able to bemultiplexed in a physical resource block, the identifying module 1406may determine whether to cause the transmission module 1408 to transmitthe connection request message and the NB-PRACH in different carriers orin a common carrier. In some aspects, the identifying module 1406 maydetermine whether to cause the transmission module 1408 to transmit theconnection request message and the NB-PRACH in different carriers or ina common carrier based at least in part on a quantity of random accesschannel subcarriers, a transmission bandwidth associated with theconnection request message, and/or the like.

The transmission module 1408 may receive, from the identifying module1406, and as data 1414, information associated with transmitting aconnection request message as data 1416 to the base station 1450. Forexample, the transmission module 1408 may transmit using at least one ofthe plurality of carriers, such as transmitting a connection requestusing the non-anchor carrier and an NB-PRACH using an anchor carrier. Insome aspects, the transmission module 1408 may transmit the connectionrequest message in a subframe not overlapping with a random accesschannel resource. For example, when the transmission module 1408 is totransmit an NB-PRACH using the random access channel resource and aresource for the connection request message collides with the randomaccess channel resource, the transmission module 1408 may transmit theconnection request message in a next available subframe. Additionally,or alternatively, the transmission module 1408 may transmit theconnection request message using a different carrier than for theNB-PRACH. In some aspects, the transmission module 1408 may multiple theconnection request message and the NB-PRACH into a common carrier.

The apparatus may include additional modules that perform each of theblocks of the algorithm in the aforementioned flow chart of FIG. 13. Assuch, each block in the aforementioned flow chart of FIG. 13 may beperformed by a module and the apparatus may include one or more of thosemodules. The modules may be one or more hardware components specificallyconfigured to carry out the stated processes/algorithm, implemented by aprocessor configured to perform the stated processes/algorithm, storedwithin a computer-readable medium for implementation by a processor, orsome combination thereof.

The number and arrangement of modules shown in FIG. 14 are provided asan example. In practice, there may be additional modules, fewer modules,different modules, or differently arranged modules than those shown inFIG. 14. Furthermore, two or more modules shown in FIG. 14 may beimplemented within a single module, or a single module shown in FIG. 14may be implemented as multiple, distributed modules. Additionally, oralternatively, a set of modules (e.g., one or more modules) shown inFIG. 14 may perform one or more functions described as being performedby another set of modules shown in FIG. 14.

FIG. 15 is a diagram 1500 illustrating an example of a hardwareimplementation for an apparatus 1402′ employing a processing system1502. The apparatus 1402′ may be a UE.

The processing system 1502 may be implemented with a bus architecture,represented generally by the bus 1504. The bus 1504 may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system 1502 and the overall designconstraints. The bus 1504 links together various circuits including oneor more processors and/or hardware modules, represented by the processor1506, the modules 1404, 1406, 1408, and the computer-readablemedium/memory 1508. The bus 1504 may also link various other circuitssuch as timing sources, peripherals, voltage regulators, and powermanagement circuits, which are well known in the art, and therefore,will not be described any further.

The processing system 1502 may be coupled to a transceiver 1510. Thetransceiver 1510 is coupled to one or more antennas 1512. Thetransceiver 1510 provides a means for communicating with various otherapparatus over a transmission medium. The transceiver 1510 receives asignal from the one or more antennas 1512, extracts information from thereceived signal, and provides the extracted information to theprocessing system 1502, specifically the reception module 1404. Inaddition, the transceiver 1510 receives information from the processingsystem 1502, specifically the transmission module 1408, and based atleast in part on the received information, generates a signal to beapplied to the one or more antennas 1512. The processing system 1502includes a processor 1506 coupled to a computer-readable medium/memory1508. The processor 1506 is responsible for general processing,including the execution of software stored on the computer-readablemedium/memory 1508. The software, when executed by the processor 1506,causes the processing system 1502 to perform the various functionsdescribed supra for any particular apparatus. The computer-readablemedium/memory 1508 may also be used for storing data that is manipulatedby the processor 1506 when executing software. The processing systemfurther includes at least one of the modules 1404, 1406, and 1408. Themodules may be software modules running in the processor 1506,resident/stored in the computer readable medium/memory 1508, one or morehardware modules coupled to the processor 1506, or some combinationthereof. The processing system 1502 may be a component of the UE 120 andmay include the memory 282 and/or at least one of the TX MIMO processor266, the RX processor 258, and/or the controller/processor 280.

In some aspects, the apparatus 1402/1402′ for wireless communicationincludes means for transmitting a random access channel using a firstcarrier, of the plurality of carriers, in a time division duplex networkfor random access, means for transmitting a connection request messageusing a second carrier, of the plurality of carriers, that is differentfrom the first carrier, and/or the like. The aforementioned means may beone or more of the aforementioned modules of the apparatus 1402 and/orthe processing system 1502 of the apparatus 1402′ configured to performthe functions recited by the aforementioned means. As described supra,the processing system 1502 may include the TX MIMO processor 266, the RXprocessor 258, and/or the controller/processor 280. As such, in oneconfiguration, the aforementioned means may be the TX MIMO processor266, the RX processor 258, and/or the controller/processor 280configured to perform the functions recited by the aforementioned means.

FIG. 15 is provided as an example. Other examples are possible and maydiffer from what was described in connection with FIG. 15.

It is understood that the specific order or hierarchy of blocks in theprocesses/flow charts disclosed is an illustration of exampleapproaches. Based upon design preferences, it is understood that thespecific order or hierarchy of blocks in the processes/flow charts maybe rearranged. Further, some blocks may be combined or omitted. Theaccompanying method claims present elements of the various blocks in asample order, and are not meant to be limited to the specific order orhierarchy presented.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” The word “exemplary” is used hereinto mean “serving as an example, instance, or illustration.” Any aspectdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects. Unless specifically statedotherwise, the term “some” refers to one or more. Combinations such as“at least one of A, B, or C,” “at least one of A, B, and C,” and “A, B,C, or any combination thereof” include any combination of A, B, and/orC, and may include multiples of A, multiples of B, or multiples of C.Specifically, combinations such as “at least one of A, B, or C,” “atleast one of A, B, and C,” and “A, B, C, or any combination thereof” maybe A only, B only, C only, A and B, A and C, B and C, or A and B and C,where any such combinations may contain one or more member or members ofA, B, or C. All structural and functional equivalents to the elements ofthe various aspects described throughout this disclosure that are knownor later come to be known to those of ordinary skill in the art areexpressly incorporated herein by reference and are intended to beencompassed by the claims. Moreover, nothing disclosed herein isintended to be dedicated to the public regardless of whether suchdisclosure is explicitly recited in the claims. No claim element is tobe construed as a means plus function unless the element is expresslyrecited using the phrase “means for.”

What is claimed is:
 1. A method of wireless communication, comprising:transmitting, by a base station, a master information block messageincluding an indicator identifying a frequency domain location parameteror a time domain location parameter for a non-anchor carrier or ananchor carrier; and transmitting, by the base station and using thenon-anchor carrier or the anchor carrier, a system information blocktype 1 (SIB1) message to a user equipment in accordance with thefrequency domain location parameter or the time domain locationparameter.
 2. The method of claim 1, wherein the SIB1 message istransmitted in a subframe 0 and a subframe 5 of alternating radio framesof the non-anchor carrier.
 3. The method of claim 1, wherein the SIB1message is transmitted in a subframe 0 of alternating radio frames ofthe anchor carrier.
 4. The method of claim 1, wherein the frequencydomain location parameter identifies a physical resource block offsetrelative to a center frequency, wherein the anchor carrier is in a firstfrequency range greater than the center frequency by the physicalresource block offset and the non-anchor carrier is in a secondfrequency range less than the center frequency by the physical resourceblock offset, or wherein the non-anchor carrier is in the firstfrequency range greater than the center frequency by the physicalresource block offset and the anchor carrier is in the second frequencyrange less than the center frequency by the physical resource blockoffset.
 5. The method of claim 1, wherein the non-anchor carrier is inat least one first physical resource block, of a resource block group,and wherein the non-anchor carrier is in at least one second physicalresource block, of the resource block group, that is contiguous to theat least one first physical resource block without one or more physicalresource blocks, of the resource block group, between the at least onefirst physical resource block and the at least one second physicalresource block.
 6. The method of claim 5, wherein the non-anchor carrierand the anchor carrier are associated with a common guard band.
 7. Themethod of claim 5, wherein the at least one second physical resourceblock is an inband physical resource block.
 8. The method of claim 1,wherein the non-anchor carrier is in a first guardband and the anchorcarrier is in a second guardband that is different than the firstguardband.
 9. The method of claim 1, wherein a size or a value for theindicator is based at least in part on a deployment mode, and whereinthe deployment mode is at least one of: an in-band deployment mode, aguard band deployment mode, or a stand-alone deployment mode.
 10. Themethod of claim 1, wherein the frequency domain location parameter orthe time domain location parameter is based at least in part on anoffset indicator identifying a resource block offset with respect to theanchor carrier.
 11. The method of claim 10, wherein the offset indicatoris based at least in part on a resource block group, and wherein theanchor carrier and the non-anchor carrier are in resource blocks of theresource block group.
 12. The method of claim 1, a frequency domainlocation for the non-anchor carrier is opposite a frequency domainlocation of the anchor carrier with respect to a center frequency. 13.The method of claim 1, wherein a subframe or frame for the SIM messageis determined based at least in part on a cell identifier or arepetition configuration.
 14. A method of wireless communications,comprising: transmitting, by a user equipment, a random access channelusing a first carrier, of a plurality of carriers, in a time divisionduplex network for random access; and transmitting, by the userequipment, a connection request message using a second carrier, of theplurality of carriers, that is different from the first carrier.
 15. Themethod of claim 14, wherein the plurality of carriers include at leastone anchor carrier and at least one non-anchor carrier used for a randomaccess channel message.
 16. The method of claim 14, wherein the secondcarrier for the connection request message is based at least in part ona carrier selection indicator from a random access response message. 17.The method of claim 14, wherein the second carrier for the connectionrequest message is based at least in part on predetermined informationor a received system information block message.
 18. The method of claim14, wherein the second carrier for the connection request message isbased at least in part on a quantity of random access channelsubcarriers and a transmission bandwidth associated with the connectionrequest message.
 19. The method of claim 14, wherein the connectionrequest message and a random access channel message are transmittedusing a common carrier of the plurality of carriers.
 20. The method ofclaim 19, wherein the connection request message is transmitted using anext available subframe not overlapping with a random access channelresource.
 21. A base station for wireless communication, comprising: amemory; and one or more processors operatively coupled to the memory,the memory and the one or more processors configured to: transmit amaster information block message including an indicator identifying afrequency domain location parameter or a time domain location parameterfor a non-anchor carrier or an anchor carrier; and transmit, using thenon-anchor carrier or the anchor carrier, a system information blocktype 1 (SIB1) message to a user equipment in accordance with thefrequency domain location parameter or the time domain locationparameter.
 22. The base station of claim 21, wherein the SIB1 message istransmitted in a subframe 0 and a subframe 5 of alternating radio framesof the non-anchor carrier.
 23. The base station of claim 21, wherein theSIB1 message is transmitted in a subframe 0 of alternating radio framesof the anchor carrier.
 24. The base station of claim 21, wherein thefrequency domain location parameter identifies a physical resource blockoffset relative to a center frequency, wherein the anchor carrier is ina first frequency range greater than the center frequency by thephysical resource block offset and the non-anchor carrier is in a secondfrequency range less than the center frequency by the physical resourceblock offset, or wherein the non-anchor carrier is in the firstfrequency range greater than the center frequency by the physicalresource block offset and the anchor carrier is in the second frequencyrange less than the center frequency by the physical resource blockoffset.
 25. The base station of claim 21, wherein the non-anchor carrieris in at least one first physical resource block, of a resource blockgroup, and wherein the non-anchor carrier is in at least one secondphysical resource block, of the resource block group, that is contiguousto the at least one first physical resource block without one or morephysical resource blocks, of the resource block group, between the atleast one first physical resource block and the at least one secondphysical resource block.
 26. The base station of claim 25, wherein thenon-anchor carrier and the anchor carrier are associated with a commonguard band.
 27. The base station of claim 25, wherein the at least onesecond physical resource block is an inband physical resource block. 28.The base station of claim 21, wherein the non-anchor carrier is in afirst guardband and the anchor carrier is in a second guardband that isdifferent than the first guardband.
 29. The base station of claim 21,wherein a size or a value for the indicator is based at least in part ona deployment mode, and wherein the deployment mode is at least one of:an in-band deployment mode, a guard band deployment mode, or astand-alone deployment mode.
 30. The base station of claim 21, whereinthe frequency domain location parameter or the time domain locationparameter is based at least in part on an offset indicator identifying aresource block offset with respect to the anchor carrier.
 31. The basestation of claim 30, wherein the offset indicator is based at least inpart on a resource block group, and wherein the anchor carrier and thenon-anchor carrier are in resource blocks of the resource block group.32. The base station of claim 21, a frequency domain location for thenon-anchor carrier is opposite a frequency domain location of the anchorcarrier with respect to a center frequency.
 33. The base station ofclaim 21, wherein a subframe or frame for the SIB1 message is determinedbased at least in part on a cell identifier or a repetitionconfiguration.
 34. A user equipment for wireless communication,comprising: a memory; and one or more processors operatively coupled tothe memory, the memory and the one or more processors configured to:transmit a random access channel using a first carrier, of a pluralityof carriers, in a time division duplex network for random access; andtransmit a connection request message using a second carrier, of theplurality of carriers, that is different from the first carrier.
 35. Theuser equipment of claim 34, wherein the plurality of carriers include atleast one anchor carrier and at least one non-anchor carrier used for arandom access channel message.
 36. The user equipment of claim 34,wherein the second carrier for the connection request message is basedat least in part on a carrier selection indicator from a random accessresponse message.
 37. The user equipment of claim 34, wherein the secondcarrier for the connection request message is based at least in part onpredetermined information or a received system information blockmessage.
 38. The user equipment of claim 34, wherein the second carrierfor the connection request message is based at least in part on aquantity of random access channel subcarriers and a transmissionbandwidth associated with the connection request message.
 39. The userequipment of claim 34, wherein the connection request message and arandom access channel message are transmitted using a common carrier ofthe plurality of carriers.
 40. The user equipment of claim 39, whereinthe connection request message is transmitted using a next availablesubframe not overlapping with a random access channel resource.
 41. Anon-transitory computer-readable medium storing one or more instructionsfor wireless communication, the one or more instructions comprising: oneor more instructions that, when executed by one or more processors of abase station, cause the one or more processors to: transmit a masterinformation block message including an indicator identifying a frequencydomain location parameter or a time domain location parameter for anon-anchor carrier or an anchor carrier; and transmit, using thenon-anchor carrier or the anchor carrier, a system information blocktype 1 (SIB1) message to a user equipment in accordance with thefrequency domain location parameter or the time domain locationparameter.
 42. The non-transitory computer-readable medium of claim 41,wherein the SIM message is transmitted in a subframe 0 and a subframe 5of alternating radio frames of the non-anchor carrier.
 43. Thenon-transitory computer-readable medium of claim 41, wherein the SIB1message is transmitted in a subframe 0 of alternating radio frames ofthe anchor carrier.
 44. The non-transitory computer-readable medium ofclaim 41, wherein the frequency domain location parameter identifies aphysical resource block offset relative to a center frequency, whereinthe anchor carrier is in a first frequency range greater than the centerfrequency by the physical resource block offset and the non-anchorcarrier is in a second frequency range less than the center frequency bythe physical resource block offset, or wherein the non-anchor carrier isin the first frequency range greater than the center frequency by thephysical resource block offset and the anchor carrier is in the secondfrequency range less than the center frequency by the physical resourceblock offset.
 45. The non-transitory computer-readable medium of claim41, wherein the non-anchor carrier is in at least one first physicalresource block, of a resource block group, and wherein the non-anchorcarrier is in at least one second physical resource block, of theresource block group, that is contiguous to the at least one firstphysical resource block without one or more physical resource blocks, ofthe resource block group, between the at least one first physicalresource block and the at least one second physical resource block. 46.The non-transitory computer-readable medium of claim 45, wherein thenon-anchor carrier and the anchor carrier are associated with a commonguard band.
 47. The non-transitory computer-readable medium of claim 45,wherein the at least one second physical resource block is an inbandphysical resource block.
 48. The non-transitory computer-readable mediumof claim 41, wherein the non-anchor carrier is in a first guardband andthe anchor carrier is in a second guardband that is different than thefirst guardband.
 49. The non-transitory computer-readable medium ofclaim 41, wherein a size or a value for the indicator is based at leastin part on a deployment mode, and wherein the deployment mode is atleast one of: an in-band deployment mode, a guard band deployment mode,or a stand-alone deployment mode.
 50. The non-transitorycomputer-readable medium of claim 41, wherein the frequency domainlocation parameter or the time domain location parameter is based atleast in part on an offset indicator identifying a resource block offsetwith respect to the anchor carrier.
 51. The non-transitorycomputer-readable medium of claim 50, wherein the offset indicator isbased at least in part on a resource block group, and wherein the anchorcarrier and the non-anchor carrier are in resource blocks of theresource block group.
 52. The non-transitory computer-readable medium ofclaim 41, a frequency domain location for the non-anchor carrier isopposite a frequency domain location of the anchor carrier with respectto a center frequency.
 53. The non-transitory computer-readable mediumof claim 41, wherein a subframe or frame for the SIB1 message isdetermined based at least in part on a cell identifier or a repetitionconfiguration.
 54. A non-transitory computer-readable medium storing oneor more instructions for wireless communication, the one or moreinstructions comprising: one or more instructions that, when executed byone or more processors of a user equipment, cause the one or moreprocessors to: transmit a random access channel using a first carrier,of a plurality of carriers, in a time division duplex network for randomaccess; and transmit a connection request message using a secondcarrier, of the plurality of carriers, that is different from the firstcarrier.
 55. The non-transitory computer-readable medium of claim 54,wherein the plurality of carriers include at least one anchor carrierand at least one non-anchor carrier used for a random access channelmessage.
 56. The non-transitory computer-readable medium of claim 54,wherein the second carrier for the connection request message is basedat least in part on a carrier selection indicator from a random accessresponse message.
 57. The non-transitory computer-readable medium ofclaim 54, wherein the second carrier for the connection request messageis based at least in part on predetermined information or a receivedsystem information block message.
 58. The non-transitorycomputer-readable medium of claim 54, wherein the second carrier for theconnection request message is based at least in part on a quantity ofrandom access channel subcarriers and a transmission bandwidthassociated with the connection request message.
 59. The non-transitorycomputer-readable medium of claim 54, wherein the connection requestmessage and a random access channel message are transmitted using acommon carrier of the plurality of carriers.
 60. The non-transitorycomputer-readable medium of claim 59, wherein the connection requestmessage is transmitted using a next available subframe not overlappingwith a random access channel resource.
 61. An apparatus for wirelesscommunication, comprising: means for transmitting a master informationblock message including an indicator identifying a frequency domainlocation parameter or a time domain location parameter for a non-anchorcarrier or an anchor carrier; and means for transmitting, using thenon-anchor carrier or the anchor carrier, a system information blocktype 1 (SIB1) message to a user equipment in accordance with thefrequency domain location parameter or the time domain locationparameter.
 62. The apparatus of claim 61, wherein the SIB1 message istransmitted in a subframe 0 and a subframe 5 of alternating radio framesof the non-anchor carrier.
 63. The apparatus of claim 61, wherein theSIB1 message is transmitted in a subframe 0 of alternating radio framesof the anchor carrier.
 64. The apparatus of claim 61, wherein thefrequency domain location parameter identifies a physical resource blockoffset relative to a center frequency, wherein the anchor carrier is ina first frequency range greater than the center frequency by thephysical resource block offset and the non-anchor carrier is in a secondfrequency range less than the center frequency by the physical resourceblock offset, or wherein the non-anchor carrier is in the firstfrequency range greater than the center frequency by the physicalresource block offset and the anchor carrier is in the second frequencyrange less than the center frequency by the physical resource blockoffset.
 65. The apparatus of claim 61, wherein the non-anchor carrier isin at least one first physical resource block, of a resource blockgroup, and wherein the non-anchor carrier is in at least one secondphysical resource block, of the resource block group, that is contiguousto the at least one first physical resource block without one or morephysical resource blocks, of the resource block group, between the atleast one first physical resource block and the at least one secondphysical resource block.
 66. The apparatus of claim 65, wherein thenon-anchor carrier and the anchor carrier are associated with a commonguard band.
 67. The apparatus of claim 65, wherein the at least onesecond physical resource block is an inband physical resource block. 68.The apparatus of claim 61, wherein the non-anchor carrier is in a firstguardband and the anchor carrier is in a second guardband that isdifferent than the first guardband.
 69. The apparatus of claim 61,wherein a size or a value for the indicator is based at least in part ona deployment mode, and wherein the deployment mode is at least one of:an in-band deployment mode, a guard band deployment mode, or astand-alone deployment mode.
 70. The apparatus of claim 61, wherein thefrequency domain location parameter or the time domain locationparameter is based at least in part on an offset indicator identifying aresource block offset with respect to the anchor carrier.
 71. Theapparatus of claim 70, wherein the offset indicator is based at least inpart on a resource block group, and wherein the anchor carrier and thenon-anchor carrier are in resource blocks of the resource block group.72. The apparatus of claim 61, a frequency domain location for thenon-anchor carrier is opposite a frequency domain location of the anchorcarrier with respect to a center frequency.
 73. The apparatus of claim61, wherein a subframe or frame for the SIB1 message is determined basedat least in part on a cell identifier or a repetition configuration. 74.An apparatus for wireless communication, comprising: means fortransmitting a random access channel using a first carrier, of aplurality of carriers, in a time division duplex network for randomaccess; and means for transmitting a connection request message using asecond carrier, of the plurality of carriers, that is different from thefirst carrier.
 75. The apparatus of claim 74, wherein the plurality ofcarriers include at least one anchor carrier and at least one non-anchorcarrier used for a random access channel message.
 76. The apparatus ofclaim 74, wherein the second carrier for the connection request messageis based at least in part on a carrier selection indicator from a randomaccess response message.
 77. The apparatus of claim 74, wherein thesecond carrier for the connection request message is based at least inpart on predetermined information or a received system information blockmessage.
 78. The apparatus of claim 74, wherein the second carrier forthe connection request message is based at least in part on a quantityof random access channel subcarriers and a transmission bandwidthassociated with the connection request message.
 79. The apparatus ofclaim 74, wherein the connection request message and a random accesschannel message are transmitted using a common carrier of the pluralityof carriers.
 80. The apparatus of claim 79, wherein the connectionrequest message is transmitted using a next available subframe notoverlapping with a random access channel resource.